UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

Quest NC-Pass Started Task name will be properly identified and/or defined to the system ACP.


Overview

Finding ID Version Rule ID IA Controls Severity
V-224526 ZNCPR030 SV-224526r868521_rule Medium
Description
Quest NC-Pass requires a started task that will be restricted to certain resources, datasets and other system functions. By defining the started task as a userid to the system ACP, It allows the ACP to control the access and authorized users that require these capabilities. Failure to properly control these capabilities, could compromise of the operating system environment, ACP, and customer data.
STIG Date
z/OS Quest NC-Pass for RACF Security Technical Implementation Guide 2022-10-07

Details

Check Text ( C-26209r868519_chk )
Refer to the following report produced by the RACF Data Collection:

- RACFCMDS.RPT(LISTUSER)

Verify that the userid(s) for the Quest NC-Pass started task(s) is (are) properly defined. If the following attributes are defined, this is not a finding.

PROTECTED
Fix Text (F-26197r868520_fix)
The ISSO working with the systems programmer will ensure the Quest NC-Pass Started Task(s) is properly identified and/or defined to the System ACP.

If the product requires a Started Task, verify that it is properly defined to the System ACP with the proper attributes.

Most installation manuals will indicate how the Started Task is identified and any additional attributes that must be specified.

The following commands are provided as a sample for defining Started Task(s):

au NCPASS name('STC, Quest NC-Pass') owner(stc) dfltgrp(stc) nopass -
data('Start CA1 TMS')